By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

#507

Description

Fixes OTel plugin X-Ray integration: cross-invocation retry span grouping, trace context extraction, and trace map display to match the JS SDK behavior.

1. Retry attempts grouped under wrong invocation - When a step failed in invocation 1 and retried in invocation 2, both operation spans had the same deterministic span ID, causing trace viewers to merge them.
2. Durable spans in separate trace — System.getenv("_X_AMZN_TRACE_ID") returned stale/null values due to JVM env caching, so the plugin fell back to an ARN-derived trace ID disconnected from Lambda's X-Ray segments.
3. Spans nested inside Lambda function instead of separate node - Missingservice.name resource and SpanKind.SERVER prevented X-Ray from creating a distinct service node for durable execution spans.

Demo/Screenshots

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Unit Tests

Have unit tests been written for these changes? Yes

Integration Tests

Have integration tests been written for these changes? N/A

Examples

Has a new example been added for the change? (if applicable) Updated existing ones.